#!/bin/bash
# Check the export.rs implementation to see if all functions are fully implemented
echo "=== Checking export_to_csv implementation ==="
ast-grep --pattern $'pub fn export_to_csv($$$) -> Result<()> {
  $$$
}'

echo -e "\n=== Checking export_to_gpx implementation ==="
ast-grep --pattern $'pub fn export_to_gpx($$$) -> Result<()> {
  $$$
}'

echo -e "\n=== Checking export_to_event implementation ==="
ast-grep --pattern $'pub fn export_to_event($$$) -> Result<()> {
  $$$
}'

echo -e "\n=== Checking for TODOs or stubs in export.rs ==="
rg -n "todo|TODO|stub|STUB|unimplemented" src/export.rs || echo "No TODOs or stubs found"

echo -e "\n=== Checking GPS/Event frame parsing implementation ==="
rg -n -A5 "gps_coordinates|event_frames" src/parser/frame.rs | head -50

echo -e "\n=== Checking if GPS G-frames are being parsed ==="
ast-grep --pattern $'\'G\' => {
  $$$
}' src/parser/frame.rs

echo -e "\n=== Checking if GPS H-frames are being parsed ==="
ast-grep --pattern $'\'H\' => {
  $$$
}' src/parser/frame.rs

echo -e "\n=== Checking if Event E-frames are being parsed ==="
ast-grep --pattern $'\'E\' => {
  $$$
}' src/parser/frame.rs

#!/bin/bash
# Check if CLI has GPS/Event parsing that the crate doesn't
echo "=== Checking CLI for GPS/Event parsing ==="
rg -n "frame_type.*'G'" src/ || echo "No G-frame parsing found"
rg -n "frame_type.*'H'" src/ || echo "No H-frame parsing found"
rg -n "frame_type.*'E'" src/ || echo "No E-frame parsing found"

echo -e "\n=== Check if CLI uses different parsing path ==="
fd -e rs . src/cli -x echo "File: {}" \; -x head -30 {}

echo -e "\n=== Look for any frame type matching in the codebase ==="
rg -n "frame_type.*=>" src/parser/frame.rs | head -20

echo -e "\n=== Check what frame types are currently handled ==="
ast-grep --pattern $'match frame_type {
  $$$
}' src/parser/frame.rs

#!/bin/bash
# Check the entire CLI structure and main entry point
echo "=== Finding CLI files ==="
fd -t f . src/ | grep -i cli || echo "No cli directory found"

echo -e "\n=== Check main.rs for CLI implementation ==="
cat src/main.rs | head -100

echo -e "\n=== Search for any GPS coordinate parsing implementation ==="
rg -n "GpsCoordinate\s*\{" src/

echo -e "\n=== Search for any Event frame parsing implementation ==="
rg -n "EventFrame\s*\{" src/

echo -e "\n=== Check types.rs for GPS/Event structures ==="
rg -n -A10 "pub struct GpsCoordinate" src/types.rs
rg -n -A10 "pub struct EventFrame" src/types.rs

#!/bin/bash
# Check where GpsCoordinate and EventFrame types are defined in the crate
echo "=== Check lib.rs exports ==="
cat src/lib.rs

echo -e "\n=== Find all type definitions ==="
rg -n "pub struct (GpsCoordinate|EventFrame|GpsHomeCoordinate)" src/

echo -e "\n=== Check if types module exists ==="
fd types.rs src/

echo -e "\n=== Check main.rs GPS parsing implementation ==="
rg -n -B3 -A15 "fn.*parse.*gps|GPS frame parsing" src/main.rs | head -80

echo -e "\n=== Check if crate re-exports these types ==="
rg -n "pub use.*Gps|pub use.*Event" src/lib.rs

#!/bin/bash
# Check if types module actually exists and what it contains
echo "=== List all files in src/ ==="
fd . src/ -t f

echo -e "\n=== Check if types is a directory ==="
ls -la src/ | grep types || echo "No types directory"

echo -e "\n=== Check parser/frame.rs imports ==="
rg -n "^use crate::types" src/parser/frame.rs

echo -e "\n=== Search for where GpsCoordinate, EventFrame, GpsHomeCoordinate are actually defined ==="
rg -n "struct GpsCoordinate" src/
rg -n "struct EventFrame" src/
rg -n "struct GpsHomeCoordinate" src/

echo -e "\n=== Check what's in the types module/file if it exists ==="
cat src/types.rs 2>/dev/null || cat src/types/mod.rs 2>/dev/null || echo "No types.rs or types/mod.rs found"

echo -e "\n=== Try to understand the compilation - does this even build? ==="
echo "Checking Cargo.toml to see if this is a workspace or single crate:"
head -20 Cargo.toml

#!/bin/bash
# Check the types directory structure
echo "=== List files in src/types/ ==="
ls -la src/types/

echo -e "\n=== Check gps.rs for GPS types ==="
cat src/types/gps.rs

echo -e "\n=== Check frame.rs for Event types ==="
cat src/types/frame.rs

echo -e "\n=== Now check main.rs GPS/Event parsing - these are CLI-only structs ==="
rg -n -B5 -A20 "^struct GpsCoordinate" src/main.rs
rg -n -B5 -A20 "^struct EventFrame" src/main.rs

echo -e "\n=== Check if main.rs has GPS/Event parsing logic that crate doesn't ==="
rg -n -A30 "'G' => {" src/main.rs | head -60
rg -n -A30 "'H' => {" src/main.rs | head -60  
rg -n -A30 "'E' => {" src/main.rs | head -60

#!/bin/bash
# Check main.rs for GPS and Event frame parsing implementation
echo "=== Search for GPS G-frame parsing in main.rs ==="
rg -n "G.*=>" src/main.rs | head -20

echo -e "\n=== Get context around line 2147 where GpsCoordinate is constructed ==="
sed -n '2130,2180p' src/main.rs

echo -e "\n=== Get context around line 2649 where EventFrame is constructed ==="
sed -n '2630,2680p' src/main.rs

echo -e "\n=== Check how many lines main.rs has ==="
wc -l src/main.rs

echo -e "\n=== Search for parse.*gps or parse.*event functions in main.rs ==="
rg -n "^fn parse.*gps|^fn parse.*event" src/main.rs -i

echo -e "\n=== Look for where frame types are matched in main.rs ==="
rg -n "match.*frame_type|frame_type.*match" src/main.rs | head -10

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:0-0
Timestamp: 2025-08-29T20:15:04.624Z
Learning: nerdCopter prefers clear positive indicators (✅) when describing fixes rather than using ❌ symbols which can be confusing when describing what was corrected in a positive context.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:1-4
Timestamp: 2025-08-29T19:52:05.099Z
Learning: nerdCopter prefers to avoid publishing personal information in license files for privacy and security reasons, as they are an individual maintainer rather than a company.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:520-521
Timestamp: 2025-08-29T19:53:41.354Z
Learning: nerdCopter uses AGPL-3.0-or-later licensing for the bbl_parser project with a dual-licensing approach that includes a separate commercial license option.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: CONTRIBUTING.md:9-14
Timestamp: 2025-08-21T20:25:45.741Z
Learning: nerdCopter prefers to keep CLA language general using "project maintainer" rather than specifying a legal entity name, as they are an individual maintainer without an associated company.

#!/bin/bash
# First, let's get the current PR description to understand what we're working with
gh pr view 6 --json title,body --jq '{title: .title, body: .body}'

#!/bin/bash
# Update the PR description to clarify scope and limitations
gh pr edit 6 --body '## Summary

This PR implements the export functionality for the BBL parser crate, making CSV, GPX, and Event exports available as library functions in addition to CLI-only access.

## Changes

### Export Implementation
- **CSV Export**: Full implementation with blackbox_decode-compatible field ordering
  - Headers CSV with flight metadata
  - Flight data CSV with I/P/S frame data, computed energy fields, and flag formatting
- **GPX Export**: Complete XML generation with coordinate filtering by minimum satellites
- **Event Export**: JSONL format with Betaflight event descriptions

### Bug Fixes
- **Critical**: Fixed `export_to_event` parameter handling for multi-log files
  - Changed from inferring `total_logs` from `log_index` to accepting explicit `total_logs: usize`
  - Fixes misclassification of `log_index = 0` in multi-log scenarios
  - Numeric suffixes now correctly appended only when `total_logs > 1`

### API Updates
- `export_to_csv`: Signature updated with implementation
- `export_to_gpx`: Added `total_logs` parameter, full implementation
- `export_to_event`: Added `total_logs` parameter, full implementation
- `parse_frames`: Return type extended to include GPS/Event vectors (currently unpopulated)
- `ExportOptions`: Added `force_export: bool` field

### Documentation & Examples
- New comprehensive examples: `csv_export.rs`, `gpx_export.rs`, `event_export.rs`, `export_demo.rs`, `multi_export.rs`
- Updated: `CRATE_USAGE.md`, `OVERVIEW.md`, `examples/README.md`
- Export functionality marked as available in both CLI and crate

## Current Limitations

⚠️ **GPS and Event frame parsing is NOT yet implemented in the crate library** (tracked in #[ISSUE_NUMBER])

- GPS (G/H frames) and Event (E frames) parsing logic currently exists only in the CLI binary (`src/main.rs`)
- The crate parser (`src/parser/frame.rs`) initializes GPS/Event vectors as empty and skips G/H/E frames
- **Impact on crate users:**
  - ✅ CSV export works (uses I/P/S frames)
  - ⚠️ GPX export returns empty data (requires GPS parsing)
  - ⚠️ Event export returns empty data (requires Event parsing)
- CLI binary maintains full functionality for all exports

## Testing

- ✅ Formatting checks passed
- ✅ Clippy lints passed  
- ✅ Unit tests passed
- ✅ Release build successful

## Follow-up Work

GPS/Event parsing migration from CLI to crate is tracked in issue #[ISSUE_NUMBER] for a future PR.'

echo "PR description updated successfully"

#!/bin/bash
# Create a new GitHub issue for GPS/Event parsing migration
gh issue create \
  --title "Migrate GPS/Event frame parsing from CLI to crate library" \
  --body "## Background

PR #6 implemented the export infrastructure (CSV, GPX, Event) for the BBL parser crate. However, GPS and Event frame parsing logic currently exists only in the CLI binary and needs to be migrated to the crate library for full functionality.

## Current State

**In the crate (\`src/parser/frame.rs\`):**
- GPS/Event vectors are initialized as empty
- G/H/E frames are skipped rather than parsed (lines 223-232)
- Export functions exist but receive empty data

**In the CLI (\`src/main.rs\`):**
- Full G-frame parsing with GPS coordinate construction (line 2147+)
- Dedicated \`parse_e_frame()\` function for Event frames (line 2491+)
- Complete Event frame construction with event descriptions (line 2649+)

## Impact

Crate users calling \`parse_bbl_file()\` receive empty vectors for GPS/Event data, even when logs contain G/H/E frames:
- ✅ CSV export works (uses I/P/S frames)
- ❌ GPX export produces no data (empty \`gps_coordinates\`)
- ❌ Event export produces no data (empty \`event_frames\`)

Only the CLI binary currently provides full export functionality.

## Required Work

1. **Migrate GPS parsing** from \`src/main.rs\` to \`src/parser/frame.rs\`:
   - Implement G-frame parsing in the \`'G'\` match arm
   - Implement H-frame parsing in the \`'H'\` match arm
   - Populate \`gps_coordinates\` and \`home_coordinates\` vectors

2. **Migrate Event parsing** from \`src/main.rs\` to \`src/parser/frame.rs\`:
   - Move \`parse_e_frame()\` logic or equivalent
   - Implement E-frame parsing in the \`'E'\` match arm
   - Populate \`event_frames\` vector with proper event descriptions

3. **Testing**:
   - Verify GPX export produces correct output from crate
   - Verify Event export produces correct output from crate
   - Ensure CLI maintains compatibility

## References

- Implemented in: PR #6
- Requested by: @nerdCopter" \
  --assignee nerdCopter \
  --label "enhancement"

echo "Issue created successfully"

#!/bin/bash
# Update the PR description to include the correct issue number
gh pr edit 6 --body '## Summary

This PR implements the export functionality for the BBL parser crate, making CSV, GPX, and Event exports available as library functions in addition to CLI-only access.

## Changes

### Export Implementation
- **CSV Export**: Full implementation with blackbox_decode-compatible field ordering
  - Headers CSV with flight metadata
  - Flight data CSV with I/P/S frame data, computed energy fields, and flag formatting
- **GPX Export**: Complete XML generation with coordinate filtering by minimum satellites
- **Event Export**: JSONL format with Betaflight event descriptions

### Bug Fixes
- **Critical**: Fixed `export_to_event` parameter handling for multi-log files
  - Changed from inferring `total_logs` from `log_index` to accepting explicit `total_logs: usize`
  - Fixes misclassification of `log_index = 0` in multi-log scenarios
  - Numeric suffixes now correctly appended only when `total_logs > 1`

### API Updates
- `export_to_csv`: Signature updated with implementation
- `export_to_gpx`: Added `total_logs` parameter, full implementation
- `export_to_event`: Added `total_logs` parameter, full implementation
- `parse_frames`: Return type extended to include GPS/Event vectors (currently unpopulated)
- `ExportOptions`: Added `force_export: bool` field

### Documentation & Examples
- New comprehensive examples: `csv_export.rs`, `gpx_export.rs`, `event_export.rs`, `export_demo.rs`, `multi_export.rs`
- Updated: `CRATE_USAGE.md`, `OVERVIEW.md`, `examples/README.md`
- Export functionality marked as available in both CLI and crate

## Current Limitations

⚠️ **GPS and Event frame parsing is NOT yet implemented in the crate library** (tracked in #7)

- GPS (G/H frames) and Event (E frames) parsing logic currently exists only in the CLI binary (`src/main.rs`)
- The crate parser (`src/parser/frame.rs`) initializes GPS/Event vectors as empty and skips G/H/E frames
- **Impact on crate users:**
  - ✅ CSV export works (uses I/P/S frames)
  - ⚠️ GPX export returns empty data (requires GPS parsing)
  - ⚠️ Event export returns empty data (requires Event parsing)
- CLI binary maintains full functionality for all exports

## Testing

- ✅ Formatting checks passed
- ✅ Clippy lints passed  
- ✅ Unit tests passed
- ✅ Release build successful

## Follow-up Work

GPS/Event parsing migration from CLI to crate is tracked in issue #7 for a future PR.

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

* **New Features**
  * CSV, GPX, and event exports available crate-wide (library + CLI), with multi-log naming and per-log outputs.
  * Multi-format export in a single run; GPX and event exports occur only when data exists.
  * Exports now emit separate header files and richer GPX/event outputs (timestamps, altitudes, JSONL-style events).

* **Documentation**
  * Expanded export docs with usage guides and examples.
  * Added example programs demonstrating CSV, GPX, event, and combined export workflows.

<sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->'

echo "PR description updated with issue #7 reference"

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:1-4
Timestamp: 2025-08-29T19:52:05.099Z
Learning: nerdCopter prefers to avoid publishing personal information in license files for privacy and security reasons, as they are an individual maintainer rather than a company.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:520-521
Timestamp: 2025-08-29T19:53:41.354Z
Learning: nerdCopter uses AGPL-3.0-or-later licensing for the bbl_parser project with a dual-licensing approach that includes a separate commercial license option.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: CONTRIBUTING.md:9-14
Timestamp: 2025-08-21T20:25:45.741Z
Learning: nerdCopter prefers to keep CLA language general using "project maintainer" rather than specifying a legal entity name, as they are an individual maintainer without an associated company.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:0-0
Timestamp: 2025-08-29T20:15:04.624Z
Learning: nerdCopter prefers clear positive indicators (✅) when describing fixes rather than using ❌ symbols which can be confusing when describing what was corrected in a positive context.

#!/bin/bash
# Check the baseline commit 4256bf1 to see what CLI exports existed
echo "=== Checking CLI export functionality at baseline commit 4256bf1 ==="
git show 4256bf1:src/main.rs | rg -n "export_to_csv|export_to_gpx|export_to_event" | head -20

echo -e "\n=== Get context around export calls at baseline ==="
git show 4256bf1:src/main.rs | rg -n -B3 -A3 "export_to_csv|export_to_gpx|export_to_event" | head -80

echo -e "\n=== Check if CSV export existed at baseline ==="
git show 4256bf1:src/export.rs | rg -n "pub fn export_to_csv" | head -5

echo -e "\n=== Check if GPX export existed at baseline ==="
git show 4256bf1:src/export.rs | rg -n "pub fn export_to_gpx" | head -5

echo -e "\n=== Check if Event export existed at baseline ==="
git show 4256bf1:src/export.rs | rg -n "pub fn export_to_event" | head -5

echo -e "\n=== Compare current CLI export calls ==="
rg -n "export_to_csv|export_to_gpx|export_to_event" src/main.rs | head -20

echo -e "\n=== Get context around current export calls ==="
rg -n -B3 -A3 "export_to_csv|export_to_gpx|export_to_event" src/main.rs | head -80

#!/bin/bash
# Check GPS and Event parsing logic in CLI at baseline vs current
echo "=== Check if GPS parsing exists at baseline (4256bf1) ==="
git show 4256bf1:src/main.rs | rg -n "'G' =>" | head -10
git show 4256bf1:src/main.rs | rg -n "GpsCoordinate" | head -10

echo -e "\n=== Check if Event parsing exists at baseline (4256bf1) ==="
git show 4256bf1:src/main.rs | rg -n "'E' =>" | head -10
git show 4256bf1:src/main.rs | rg -n "EventFrame" | head -10

echo -e "\n=== Check GPS parsing in current branch ==="
rg -n "'G' =>" src/main.rs | head -10
rg -n "GpsCoordinate \{" src/main.rs | head -5

echo -e "\n=== Check Event parsing in current branch ==="
rg -n "'E' =>" src/main.rs | head -10
rg -n "EventFrame \{" src/main.rs | head -5

echo -e "\n=== Check if CLI still collects GPS/Event data ==="
rg -n "gps_coordinates|event_frames" src/main.rs | head -30

#!/bin/bash
# Check export function signatures at baseline vs current
echo "=== Export function signatures at baseline (4256bf1) ==="
git show 4256bf1:src/export.rs | ast-grep --pattern 'pub fn export_to_csv($$$)'
git show 4256bf1:src/export.rs | ast-grep --pattern 'pub fn export_to_gpx($$$)'
git show 4256bf1:src/export.rs | ast-grep --pattern 'pub fn export_to_event($$$)'

echo -e "\n=== Export function signatures in current branch ==="
ast-grep --pattern 'pub fn export_to_csv($$$)' src/export.rs
ast-grep --pattern 'pub fn export_to_gpx($$$)' src/export.rs
ast-grep --pattern 'pub fn export_to_event($$$)' src/export.rs

echo -e "\n=== Check if CLI still has its own export path or uses crate exports ==="
rg -n "fn main" src/main.rs | head -5
rg -n "use.*export" src/main.rs | head -20

echo -e "\n=== Verify CLI passes GPS/Event data to exports ==="
rg -n -B5 -A10 "export_to_gpx\(|export_to_event\(" src/main.rs | head -60

#!/bin/bash
# More thorough check of how CLI does exports at baseline vs current
echo "=== Check baseline (4256bf1) CLI export logic ==="
git show 4256bf1:src/main.rs | rg -n -A50 "fn main" | rg -A3 "CSV|GPX|Event|export" | head -80

echo -e "\n=== Check if baseline had inline export code in main() ==="
git show 4256bf1:src/main.rs | rg -n "write_csv|write_gpx|write.*event" | head -20

echo -e "\n=== Check current CLI export logic ==="
rg -n -A50 "fn main" src/main.rs | rg -A3 "CSV|GPX|Event|export" | head -80

echo -e "\n=== Search for any write/export operations in current main.rs ==="
rg -n "write_|File::create|BufWriter" src/main.rs | head -30

echo -e "\n=== Check if there's a separate export function in CLI ==="
rg -n "fn.*export|fn.*write" src/main.rs | head -20

#!/bin/bash
# Check the actual export implementation - maybe CLI has inline exports
echo "=== At baseline, check if exports were inline or function calls ==="
git show 4256bf1:src/main.rs | rg -n -B5 -A20 "CSV output|GPX output|Event output|headers.csv|\.gpx|\.jsonl" | head -100

echo -e "\n=== Current branch, check if exports are inline or function calls ==="
rg -n -B5 -A20 "CSV output|GPX output|Event output|headers.csv|\.gpx|\.jsonl" src/main.rs | head -100

echo -e "\n=== Check the complete flow from main() at baseline ==="
git show 4256bf1:src/main.rs | sed -n '520,700p'

echo -e "\n=== Check the complete flow from main() in current ==="
sed -n '520,700p' src/main.rs

#!/bin/bash
# Check if CLI actually invokes exports - search for the export flow
echo "=== Look for where parsed data is used in baseline ==="
git show 4256bf1:src/main.rs | rg -n -A10 "parse_bbl_logs" | head -60

echo -e "\n=== Look for where parsed data is used in current ==="
rg -n -A10 "parse_bbl_logs" src/main.rs | head -60

echo -e "\n=== Check if exports happen after parsing in baseline ==="
git show 4256bf1:src/main.rs | rg -n -C8 "for.*log in.*logs|for log in" | head -80

echo -e "\n=== Check if exports happen after parsing in current ==="
rg -n -C8 "for.*log in.*logs|for log in" src/main.rs | head -80

#!/bin/bash
# Find where GPX and Event exports are actually invoked in CLI
echo "=== Find GPX export invocation at baseline ==="
git show 4256bf1:src/main.rs | rg -n -B10 -A10 "export_gpx_file|gpx_filename" | head -100

echo -e "\n=== Find Event export invocation at baseline ==="
git show 4256bf1:src/main.rs | rg -n -B10 -A10 "export_event_file|event_filename" | head -100

echo -e "\n=== Find GPX export invocation in current ==="
rg -n -B10 -A10 "export_gpx_file|gpx_filename" src/main.rs | head -100

echo -e "\n=== Find Event export invocation in current ==="
rg -n -B10 -A10 "export_event_file|event_filename" src/main.rs | head -100

#!/bin/bash
# Check the parse_bbl_file_streaming function which is called from main
echo "=== Check parse_bbl_file_streaming at baseline ==="
git show 4256bf1:src/main.rs | rg -n "fn parse_bbl_file_streaming" -A100 | head -120

echo -e "\n=== Check parse_bbl_file_streaming in current ==="
rg -n "fn parse_bbl_file_streaming" src/main.rs -A100 | head -120

#!/bin/bash
# Look at the complete export flow in parse_bbl_file_streaming
echo "=== Baseline: Where are GPX/Event exports called in streaming function ==="
git show 4256bf1:src/main.rs | sed -n '1256,1400p'

echo -e "\n=== Current: Where are GPX/Event exports called in streaming function ==="
sed -n '1256,1400p' src/main.rs

echo -e "\n=== Baseline: Check end of parse_bbl_file_streaming ==="
git show 4256bf1:src/main.rs | rg -n "fn parse_bbl_file_streaming" | head -1
git show 4256bf1:src/main.rs | sed -n '2366,2410p'

echo -e "\n=== Current: Check end of parse_bbl_file_streaming ==="
rg -n "fn parse_bbl_file_streaming" src/main.rs | head -1
sed -n '2366,2410p' src/main.rs

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:1-4
Timestamp: 2025-08-29T19:52:05.099Z
Learning: nerdCopter prefers to avoid publishing personal information in license files for privacy and security reasons, as they are an individual maintainer rather than a company.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:520-521
Timestamp: 2025-08-29T19:53:41.354Z
Learning: nerdCopter uses AGPL-3.0-or-later licensing for the bbl_parser project with a dual-licensing approach that includes a separate commercial license option.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: CONTRIBUTING.md:9-14
Timestamp: 2025-08-21T20:25:45.741Z
Learning: nerdCopter prefers to keep CLA language general using "project maintainer" rather than specifying a legal entity name, as they are an individual maintainer without an associated company.

Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:0-0
Timestamp: 2025-08-29T20:15:04.624Z
Learning: nerdCopter prefers clear positive indicators (✅) when describing fixes rather than using ❌ symbols which can be confusing when describing what was corrected in a positive context.